The Big Picture
You have now covered the entire Waterfall Lifecycle. This methodology is a sequential, linear approach where each phase must be completed before the next begins.
Here is a summary of the six distinct phases:
1Requirements – Gather and analyze what the system needs to do.
2System Design – Plan the look, functionality, and technical architecture.
3Implementation – Code, build infrastructure, and create databases.
4Testing – Verify the system is robust, reliable, and meets requirements.
5Deployment – Install the system and train users.
6Maintenance – Provide ongoing support, bug fixes, and new features.
Now, let's test your understanding of how these phases work together in real-world scenarios.
Scenario 1: Choosing the Right Method
The Scenario: A small bakery wants to upgrade its two office computers to a new, very standard point-of-sale (POS) system. The requirements are fixed, the hardware is known, and the staff will need minimal training.
Which methodology is best suited for this project?
Why B is correct: The textbook states Waterfall is useful for "small or simple projects with few requirements" and "where the requirements are clearly defined and unlikely to change."
The bakery has a standard, fixed upgrade (like the server example in the text), making it ideal for Waterfall. Complex, dynamic, or unknown projects (A, C, D) are poor fits.
Scenario 2: Gathering Requirements
The Scenario: An IT team is in Phase 1. They need to understand exactly how the warehouse staff currently process inventory returns, including the physical steps and the bottlenecks. They want to see it with their own eyes to understand the workflow.
Which requirements gathering method should they use?
Why C is correct: The textbook defines Observation as "Directly watching stakeholders in the intended environment." It allows the team to "more easily identify current processes, challenges and user needs" by seeing the real-world workflow, rather than relying on what people say in a survey or focus group.
Scenario 3: Design vs. Implementation
The Scenario: A project is underway. A designer is currently mapping out a low-fidelity layout of the new mobile app's login screen to get early feedback from users on the structure. They are not writing code yet.
Which phase is the designer in?
Why B is correct: Wireframing and prototyping are explicitly listed under "System Design phase activities." They allow designers to "explore different design solutions, gather feedback early in the design process and refine interactions before final implementation."
Scenario 4: Testing & Deployment
The Scenario: A QA team has finished testing the entire system. It is now being installed on the client's physical servers, and the company is scheduling training sessions for the end-users and IT support staff.
Which phase is the project currently in?
Why C is correct: The text states that during Deployment/Installation: "Any new software systems that have been developed will now be installed onto the target machines ready for use by the company" and "Before a system goes live, the development company will provide key stakeholders with training on how to use the system."
🎉 Congratulations! You have mastered the Waterfall Methodology!
Final Recap:
• Strengths: Predictable, structured, and excellent for fixed, simple projects.
• Weaknesses: Rigid, no room for changing requirements, and high risk if a requirement is missed early on.
• Core principle: You cannot move to the next step until the current step is 100% complete.
You are now ready to apply this knowledge to any IT project methodology assessment!